*************************************************** ** NP00642 FILE ** ** DATE = 10/10/96 ** PHONE = 8-444-0017 ** CONTACT = SANDY PETERSON ** C/T = RD0011 ** USER = SANDYPE NODE = RALVM29 ** *************************************************** APARTXT NA02259 = passes through XID on T/R stating maxout 7 is being used when in reality a hard coded value of 2 is used. This causes a performance throughput problem when the workstation is configured for a maxin of 7. APARTXT NA02524 = I entered sysman, changed the SNMP System Name via the System Manager Configuration Utility, and applied the change. I then tried to retrieve the current configuration using the config tool, May 28 version. I get the error message, Internal execution error: More bytes read from stream than expected. This problem is simular to one found by Mac in bootcamp. APARTXT NA02576 = DLSw seems to get in trouble and has difficulty recovering when there is lots of broadcast traffic flowing causing the analyst's queue to back up. It takes the analyst too long to get to the queued up messages, and by the time it gets to them, the message is so old that it is virtually meaningless. Code has been added to let the analyst turn its message queue "on" and "off". When its queue gets to a certain length (configurable thru ChangeDLSwParms), it will turn off its queue, allowing the analyst to process the queued messages in a timely manner. While the queue is turned off, all broadcast messages destined for the analyst queue will simply (and quickly!) be tossed away (remember broadcast traffic is not guaranteed), giving the analyst more time to execute and process those queued messages. When the analyst has gotten its queue to a reasonable length (again configurable), it will turn its queue back on allowing broadcast traffic to be processed. Also added with this change counters so we can keep track of the load entering DLSw and it performance. This change does not affect IFRAMEs since they do not go thru the analyst. Since this "overload" feature is configurable, it is possible to have the DLSw code function as it does today. APARTXT NA02425 = LAN8041 message in the error log incorrect. Should say that : No Response to IFrame, Retry's Exhausted, Dropping Link Station. APARTXT NA02493 = Getting underrun errors when using dual port ethernet cards and transferring IP data port-to-port when segmenting is being used. The problem can be created by pinging with a 1500 byte ping frame through the port-to-port of the card into a network that is defined for 1492 frame size. Pinging with more than 4000 bytes will cause the error in almost every instance. APARTXT NA02508 = It would be nice to have CONVSUMM output the sequence numbers in their correct decimal value. This would make it much easier to see the incremental updates of the sequence numbers. APARTXT NA02507 = Add EBCDIC translation to dump formatters APARTXT NA02547 = When a 6611 user codes an XID for the Switched SDLC Call In function, it should overlay whatever is provided by the dialed in PU Type 2. Before this fix, when XID 00000000 was coded in Personal Communications 4.0 PU T2 and the proper XID was coded in 6611, the PU did not properly connect to VTAM. APARTXT NA02545 = The cost-reduced ethernet adapters have significant number of underruns on transmits, especially during high traffic with large frames. APARTXT NA02548 = When the ANSTONE feature was configured for SDLC Switched Call In, sometimes the connection would not work. APARTXT NA02537 = Internal enhancements APARTXT NA02544 = DLS fails to free buffers when more than 1000 sessions are simultaneously in the session establishment state. Each additional session est. attempt will cause a buffer release failure. The condition is cumulative until DLS is restarted. APARTXT NA02577 = An option has been added to CONVSUMM to group the output by either MAC ADDRs and SAPs or by MAC ADDRs only. The default will be MAC ADDRs only. By using the -s flag on invocation, the output will be grouped by MAC ADDR and SAPs, as is done today. APARTXT NA02551 = On error, ospfquery core dumps. Also ospfquery is dependent on smux.r66d being active and doesn't need to be. APARTXT NA02597 = V1R4 allowed one to have duplicate OSPF network ranges. The Config Tool will not let you enter these but customers with duplicates configured prior to IP address checking in V1R2 could have GateD parse errors. APARTXT NA02598 = Extraneous messages when rejecting PTF from fastpath APARTXT NA02552 = Thru SYSMGR, configuring the ipx network number in hexdecimal format got a failure return code indicated that the value has to be in hex. value which it actually is. APARTXT NA02555 = fast path command appn set -mode_name COS_number mode_name fails with error "appncfg not found" APARTXT NA02580 = Inventory/prereq changes for FX64001. APARTXT NA02563 = Strip GateD to save space in V1R4 PTF P640 Migration PTF. APARTXT NA02566 = Picking up psna_r2 defects for egpe APARTXT NA02561 = About every 2 weeks router cannot support dls connection to a specific netbios server. Server is configured with a default router. APARTXT NA02564 = Router running FX60113 is collecting RmtDscPnd and HltRpAkPd states. Sessions cannot be established after such states have been hung for all the paths available. Problem occurs between IBM andIBM and IBM and BayNetworks routers. APARTXT NA02581 = Dynamically changing the box address leaves the old box address on the card. APARTXT NA02582 = Enhance dlstools output to describe the conversation states of the conversation table more literally. This entails moving the queue info into another conversation option, "-QUEUES". APARTXT NA02583 = This defects covers Hoe Trinh's IP card code changes for IP Helper Address. APARTXT NA02600 = ifconfig status does not display the up/down status of point-to-point links on a non-fully meshed FR interface. 2) ifconfig status does not show the "framing method" (PPP, FR, SMDS) configured on serial interfaces. APARTXT NA02587 = Enhancement for ospf_sock APARTXT NA02588 = Since SCRAM no longer flushes routes on detection of a new interface (perf. improvement) a test program is required to allow routes to be flushed in the event something get's messed up (hopefully we won't have to use this). The new program also allows one to add or delete an IP route from the card adapter tables. APARTXT NA02584 = Routers can get stuck in 2-Way after if frame relay DLCI go up and back down during frame relay network bring up. APARTXT NA02589 = frame relay sap not changed when configured APARTXT NA02601 = psna load APARTXT NA02593 = cp to cp sessions are setup, cp capabilities are exchanged, when topology tdu's begin flowing between nodes, a error is found in a tdu, cv45 is only 2 bytes long, other node characteristics information is missing, then cp to cp sessions are unbound. APARTXT NA02594 = sense from 6611 dlur node indicating out of storage when only 37 sessions up and shared storage is at 3.5meg appn is allocating too much storage for each session. APARTXT NA02602 = Internal Enhancements for NP00642 APARTXT NA02550 = IPX traffic was not supported in the first release of SMDS code. APARTXT NA02549 = this is a feature, not a defect, so question does not make sense. this is the switched SDLC call in line item APARTXT NA02578 = This feature will track the design change to DLSw that will enable DLSw to do a selective wancast of Netbios broadcast traffic. If and when a CapEx Msg is received from the DLSw Partner, the Supported Sap List Control Vector will be scanned and the info about the netbios sap being supported or not will be saved. The analyst will then use this info when wancasting for netbios broadcast traffic and not send the message if the partner does not support the netbios sap. APARTXT NA02599 = The main purpose of this feature was to add support for system manage r commands related to IPX over SMDS. System Manager, the SMDS daemon an d SMDS adapter code was modified to accomplish this. In addition, chang es were made in the config daemon, smds daemon and smds adapter code to decou ple IP and IPX so that IPX could run without IP configured. Finally, a fi x was added so that IPX packets whose destination from the SMDS link was no t the next hop could be routed successfully. ENDSET COMPID FOR PTF NP00642 = 564801600,140 PRODID FOR PTF NP00642 = 5648016,Multiprotocol Network Program PREREQ FOR NP00642 = NONE ENDSET COREQ FOR NP00642 = NONE ENDSET SUP FOR NP00642 = NONE ENDSET IFREQ FOR NP00642 = NONE ENDSET MEMO TO USERS = +---------------------------------------------------------------+ | | | | | MEMO FOR NP00642 | | | | 642 01 | | | | | +---------------------------------------------------------------+ CONTENTS OF THIS MEMO _____________________ o Description of Supersede and Prerequisite PTFs o Installation instructions for NP00642 o Engineering PTFs with contents included in Production PTFs o New Function Contained in PTF NP00642 - SMDS IPX - SDLC Switched Dial In - UDP Broadcast Forwarding (IPHelper) - All NP00640 Function (described below) o New Function Contained in PTF NP00640 - Option set 1116 - NNS support for DLUR EN - BGP-4 - SMDS Integration (IP Only) - Multiple IP Addresses - IP Filters - IP Keep Alive - IP TCP Re-Transmission Control - Router Access via Bridged EN Port - APPN APING - IPX PACING AND LARGER SAP/RIP TABLES - Bridge Priority Queueing - System Manager Enhancements - Configuration Enhancements SUPERSEDE AND PREREQUISITE PTFS ________________________________ NP00642 is not a supersede PTF. There are no prerequisite PTFs for NP00642. Any user at base V1R4 can apply this ptf. Having PTFs NP00620, NP00623, NP00625 or NP00640, though not required, will not prevent NP00642 from being applied. However, a user having PTFs NP00627 or beyond will have to remove those PTFs before NP00642 can be applied. All the fixes contained in NP00640, NP00625, NP00623 and NP00620 are contained in NP00642. Users at any release levels other than V1R4 must migrate to that level (using NP99932 or NP99931) and be committed at that level before applying NP00642. Note: NP99932 is an MES Upgrade to V1R4 at PTF level NP00625 and is current. NP99931 is an MES Upgrade to V1R4 base. PTF INSTALL INSTRUCTIONS FOR NP00642 ____________________________________ Potential problems or delays in the installation procedure can be avoided if you perform certain actions first. CLEANING UP THE 6611 TRANSFER DIRECTORY Receiving installation files places them in the transfer directory of the 6611. If you know you have unnecessary files in the transfer directory (such as outdated dumps or reports), delete the files before beginning the installation. Refer to "Delete Transfer Directory Files" in the Operations chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for details. STOPPING TRACES Before beginning the installation process for any update, stop all trace activities. Active traces might cause installation to fail because of insufficient space. Refer to the Problem Determination chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for information on stopping traces. HANDLING DEVELOPMENT PTFS Before beginning the installation process for any software update, check to see if you have any development PTFs on your system. Development PTFs may be identified as containing the characters FX in their names, for example: Name: mpnp.obj NP00001 ---------------------- Fix ID Release ========================== FX00001 01.01.0000.0001 If you know that you have development PTFs on your system, call your IBM Support Center and provide the following information: o The development PTFs that are already on your system o The software updates you wish to install INSTALLING SOFTWARE UPDATES Software updates are installed from the transfer directory using the Software Installation and Maintenance Facility of the Multiprotocol Network Program V1R3 Supplement(SD35-0238). This is a multiphase process that permits the software updates to be tested before making them a permanent part of the Multiprotocol Network Program. When updating software, the first step after importing the software update is to apply the software update. After a software update is applied to a 6611, it can be activated at a later time. You can specify the maintenance level and the date and time of the activation. The 6611 will be re-IPLed at activation time. Thus, the application of a PTF is not directly coupled with the re-IPL of the router. Any software update that is applied, but not activated in the currently running 6611, can be rejected at any time. A software update must be active before it can be committed. Warning: When you commit the software update, the change is permanent. There are several rules to consider when installing software updates that have dependencies: o Software updates cannot be applied until their prerequisite software updates have been applied. o Applied software updates cannot be committed until their prerequisite software updates have been committed. Possible Messages When Applying PTFs: If there is not sufficient space available, you will see a system message similar to: Installation failed. Please press enter to view the detailed information. (Assuming Enter is pressed, this detailed message is displayed:) installp could not complete because there is not enough space in file system /usr. It needs 476 more 1K blocks. The space available in /usr is less than the minimum required for this operation. The selected install operation will not be started now. Press Enter to continue. If there are more than 1000 1K blocks free in each file system, then you will see different messages depending on whether there was sufficient room for the PTFs you selected to apply. NOTE: If you have insufficient space in the file systems other than /tmp and you have commited all prior PTF's, you must contact IBM service. IBM service will make the appropriate adjustments to the file systems. If you select multiple PTFs to be applied and there is room for some, but not all, only the ones that fit will be applied. The log file pd_update.log in the transfer directory will inform you of this. To perform software updates from the System Manager: 1. Log in to the System Manager using a controlling user ID. 2. Select Software Installation and Maintenance on the System Manager main menu. Follow this procedure to install your software update using the System Manager: Step 1 Your software update is sent to you on diskettes or tape. The software update must be moved to the transfer directory for installation. Before proceeding, refer to "Recommended Software Pre-Installation Actions" for suggested actions if you have not already done so. Step 2 Select Receive Software Updates from the Software Installation and Maintenance menu to move the update files to the transfer directory in the 6611. These import methods are available: * FTP * Modem * Tape * Diskette Before receiving any software files, the system validates that enough space is available in the transfer directory. NOTE: Steps 3 and 4 are optional steps for informational purposes only and are not required for this installation Step 3 Select List Software Updates in the Transfer Directory to view a list of the software in the transfer directory of the 6611, Step 4 Select List All Problems Fixed by Software Updates to list the problems fixed by the software updates in the transfer directory. Step 5 Select Apply Software Updates to install the software updates on the 6611. The installation ends without a re-ipl, and you are returned to the Software Installation Maintenance menu. Step 6 Select Activate Applied Software Updates to activate the applied software updates. In the first selection screen, select NP00640. In the second selector screen you must use "none" as a selection if that is the only choice or if you wish to select no EPTF's. COMMITTING THE SOFTWARE UPDATE (PTF NP00642) CAUTION: When you commit the software update, the change is permanent. You will not be able to reverse the commit. When PTF NP00642 is committed NP00620, NP00623, NP00625 or NP00640 if present WILL NOT BE automatically committed. They cannot, however, be activated, and can only be rejected, thereafter. Step 1 Select Commit Active Software Updates to commit the activated software updates. Refer to Chapter 5 "Software Installation and Maintenance" in the Multiprotocol Network Program Supplement Version 1 Release 3 (SD35-0238) more installation information. ------------------------------------------------------------ Installation of PTF NP00642 along with the prerequisite and corequisite PTF's, will alleviate the need for the engineering PTF's listed below to reside on your machine. NOTE: If you are currently running with an Engineering PTF that is not on the list below, contact your IBM Service representative for possible additional instructions. FX62001 FX62002 FX62301 FX62302 FX62303 FX62501 FX62502 FX64001 The Functional Enhancements described below were available in PTF NP00640 unless otherwise noted. All functional enhancements in NP00640 are also available in NP00642 which replaces NP00640... ----------------------------------------- * NNS support for DLUR EN - Option Set 1116 ----------------------------------------- This feature enables the 6611, when configured as an APPN NN, to understand when a DLUR EN that supports Option Set 1116 registers its LUs. The Dependent LU Requestor (DLUR) architecture has been enhanced to allow DLUR End Nodes to register their LUs with a Network Node Server so that searches do not need to take place each time. This can cut down significantly on unneeded network searches. The 6611 cannot be configured as an End Node but now has the Network Node Server support to receive the LU registration and recognize the LU as a DLUR LU. ----------------------------------------- * BGP-4 ----------------------------------------- Border Gateway Protocol (BGP) uses policies to control the advertisement of routes across organization (autonomous system) boundaries. Thus BGP is used to interface an organization's network with one or more providers of Internet service. BGP is also used by service providers to interface with each other. Note that BGP can also be used to control the distribution of route topology information within a large private network. BGP-4 is described in RFC-1657. The key difference between it and BGP-3 has to do with aggregation of routes. With BGP-3 all advertisements must be for classical network addresses. BGP-4 allows contiguous addresses to be aggregated. Any address prefix can be advertised as long as the advertiser provides routes to all the included addresses. So the hope is that providers will be able to aggregate the network addresses of their users and reduce the large number of routes that must be advertised today for complete information about large networks. BPG-4 also facilitates CIDR (Classless Inter-Domain Routing) since it allows an organization to advertise a block of class C networks with a single advertisement. CIDR was shipped on the 6611 in V1R4. The 6611 implementation of BGP-4 has the following limitations: - It does not support the full Internet routing table (35-40,000 routes). - The BGP-4 MIB is supported as SNMPv1 rather than SNMPv2 as specified in the RFC. ----------------------------------------- * SMDS Integration (IP Only) ----------------------------------------- Switched Multimegabit Data Service is a high performance, connection-less, public switched data service designed to interconnect LANs and provides LAN-like features and performance across Wide Area Networks. SMDS uses cell relay switching technology. Generic system requirements are defined in Bellcore specification TR-TSV-000722. RFC-1209 defines the handling of IP and ARP packets and encapsulation, and SMDS complies with IEEE standard 802.6 MAN. The service provides individual, group and ARP addresses at DS1 (1.5Mbps), DS3 (45Mbps) and SONET (155Mbps) speeds. It also supports a slower speed option of 56-64Kbps. The 6611 supports speeds from 56Kbps through DS1. SMDS was initially shipped on the 6611 as a PRPQ (Programming Request for Price Quotation). In PTF NP00640, the code was incorporated into the mainstream 6611 MPNP code and supported IP only. In PTF NP00642, SMDS supports IPX as well as IP. The SMDS WAN protocol can be configured on A25 or A47 two or four port serial adapters or on either LAN/WAN combo adapter. It is not supported on the old serial adapters. **************************************************************** *SUPPLEMENT TO 6611 NETWORK PROCESSOR OPERATION POCKET GUIDE * **************************************************************** **************************************************************** *** If you receive this document in softcopy format and *** *** print it, symbols, for example, in fast path commands, *** *** may not resolve accurately for some printers. Please *** *** refer to the IBM MPNP Operations and Problem Management *** *** Guide, SC31-6691 for a description of how to use these *** *** commands. *** **************************************************************** This chapter supplements the information in Chapter 4 of the 6611 Network Processor Operation Pocket Guide, GX27-3909. These guidelines describe how fast-path commands are structured: * Brackets ([ ]) surround: - Groups of options separated by an |, when only one option in the group can be specified (for example, [-diskette|-tape]) - Groups of options separated by an &|, when one or more options in the group can be specified (for example, l(-packet) &| -frame]) * Parameters are in double quotation marks (" "). * Parentheses (( )) surround any defaults for the subobjects, actions (depending on the subobject), and options. * Braces ({ }) surround options and parameters that are not required. *************************************************************** SMDS Commands Use the SMDS commands to: * View the SMDS ARP Tables * Delete all entries from the SMDS ARP Tables * Clear SMDS statistical counters * View the SMDS individual address, group address and ARP address associated with a given interface * View the SMDS statistics for a given interface * List interfaces configured for SMDS * View the SMDS MIB Error table for a given interface Object Abbreviations: smds: SMDS, sm Subobject Abbreviations: address: addr, ad arp: a statistics: statistic, stat, s Action Abbreviations: clear: clr, c delete: del, d list: l view: v Option Abbreviations: -active: -act, -a -all -IP -ip -IPX -ipx -miberr: -me Summary of SMDS Commands smds address (view){-log} "interface" - View the SMDS individual address, group address and ARP address associated with a given interface. smds arp delete [(-all)|-IP|-IPX] "interface" - Delete entries from the SMDS ARP Tables. smds arp (view) {-log} [(-IP)|-IPX] "interface" - View the specified SMDS ARP Table. smds list {-active} {-log} "interface" - List the serial interfaces configured for SMDS. smds statistics clear "interface" - Clear SMDS statistical counters. smds statistics (view) {-log} "interface" - View the SMDS statistics for a given interface. smds statistics (view) -miberr {-log} "interface" - View the SMDS MIB Error table for a given interface. ----------------------------------------- * Multiple IP Addresses (MIA) ----------------------------------------- Prior to this function, the 6611 supported only one IP address per physical interface. This function supports multiple IP addresses on single token ring and ethernet ports. The 6611 implementation of MIA has the following limitations: - MIA is only supported on LAN adapters (token ring and ethernet). - A maximum of 10 IP addresses is allowed per physical interface with a total of 66 addresses per router. The network (sub-network) portion of the secondary address of each interface must be unique within the router. - Each IP address may have its own subnet mask. - No subnet overlapping is permitted. This restriction does not apply to the loop-back address (127.0.0.1) or the multicast address (224.0.0.x). ----------------------------------------- * IP Filters ----------------------------------------- This function allows a customer to enable traffic such as telnet and ftp (both requests and responses) to flow in one direction but not in the other. An example would be where a user might want to telnet/ftp out to the Internet but where the customer might want to restrict external access into his/her network. Customers can now choose filtering based on TCP/UDP source port, destination port or both. Prior to NP00640, filtering had to be symmetrical, that is, the restrictions had to be the same in both directions. ----------------------------------------- * IP Keep Alive ----------------------------------------- The IP "keep alive" timeout period can now be tuned by the customer to enhance the stability of some networks. Prior to PTF NP00640, this value could not be altered. ----------------------------------------- * IP TCP Re-Transmission Control ----------------------------------------- Prior to NP00640, the 6611 always attempted 12 retransmissions prior to closing a TCP session. The maximum time between retransmissions was fixed at 64 seconds. With this function, the customer can alter these values via the Configuration Tool to provide better network stability in certain situations. ----------------------------------------- * Router Access via Bridged EN Port ----------------------------------------- A bridged Ethernet port can be accessed via telnet for the purposes of logging into the box. Prior to this PTF, this function was only available on token ring ports. ----------------------------------------- * SDLC MIB ----------------------------------------- Ther are two new SNMP SDLC traps that provide port and link station (LS) status. Port UP/DOWN status has also been made more accurate. Note that this function was also provided in V1R4 via PTF NP00623 and in V1R3 via PTF NP00387. ----------------------------------------- * APPN APING ----------------------------------------- An "APING" can be issued from a 6611 to any other APPN device supporting APING including another 6611, VTAM or Comm Manager/Server. APING may also be issued from one of these latter devices to a 6611. The target device does not have to be physically adjacent to the originator as long as an APPN "route" is active between the two devices. APING can be issued from a 6611 via the System Manager fastpath or a via a System Manager screen. ----------------------------------------- * IPX Pacing and Larger SAP/RIP Tables ----------------------------------------- IPX has been enhanced to provide SAP and RIP tables with 4096 entries which is twice the size of the tables in V1R4 and prior releases. In addition, IPX SAP and RIP pacing has been added to the PPP interface. ----------------------------------------- * Bridge Priority Queueing ----------------------------------------- This function provides bridge filtering that can be applied to determine the priority of SEND frames as high/medium/low. ----------------------------------------- * Switched SDLC Dial In - NP00642 ----------------------------------------- Allows PU Type 2.0 dial in to a 6611. ----------------------------------------- * UDP Broadcast Forwarding - NP00642 ----------------------------------------- This function (also know as IPHelper) allows configuring a destination address rather than a local port address as the target for forwarded UDP broadcast packets. Thus one can configure the DHCP/BOOTP server address as the target for a DHCP/BOOTP client and not worry about either the path to the server or the increased broadcast traffic on intermediate networks. ----------------------------------------- * System Manager Enhancements ----------------------------------------- The System Manager has been enhanced to provide screen and fastpath commands for APPN network debugging and other functions. Note that APPN fastpath commands were also provided in V1R4 PTF NP00623. ----------------------------------------- * Configuration Tool ----------------------------------------- The 6611 Configuration Tool has been enhanced to support the new functions in PTF NP00642. This Tool may also be used to configure 6611 V1R4 routers. A Configuration UPGRADE is NOT required. The customer is warned if he/she attempts to configure function only available in PTFs NP00640 or NP00642. In most cases, if the customer chooses to ignore this warning and configures enhanced function on a V1R4 router without the appropriate Enhanced Function PTF (NP00640 or NP00642), the new function will be ignored -- however, this is not guaranteed. Additional information specific to the new Configuration Tool can be found in the README file on the Configuration Tool installation diskettes. END OF MEMO - NP00642 ENDSET LABELTXT Selective Fix Package For use on MPNP V1, R4.0 only ENDSET ***************************************************